-
Notifications
You must be signed in to change notification settings - Fork 321
Override tkn-cli-srv image #10339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Override tkn-cli-srv image #10339
Conversation
🤖 Gemini AI Assistant AvailableHi @aThorp96! I'm here to help with your pull request. You can interact with me using the following commands: Available Commands
How to Use
PermissionsOnly OWNER, MEMBER, or COLLABORATOR users can trigger my responses. This ensures secure and appropriate usage. This message was automatically added to help you get started with the Gemini AI assistant. Feel free to delete this comment if you don't need assistance. |
|
🤖 Hi @aThorp96, I've received your request, and I'm working on it now! You can track my progress in the logs for more details. |
e3caeab to
098fb6e
Compare
|
/lgtm |
|
/approve |
🤖 Pipeline Failure AnalysisCategory: Timeout The E2E tests timed out due to prolonged application deployment and synchronization processes, potentially exacerbated by underlying Argo CD ApplicationSet synchronization issues and Tekton component errors. 📋 Technical DetailsImmediate CauseThe Contributing FactorsSeveral factors may have contributed to the prolonged execution:
ImpactThe timeout prevented the completion of the E2E tests, meaning the pipeline could not validate the functionality and stability of the deployed application infrastructure. This failure blocks the main branch integration and deployment verification. 🔍 Evidenceappstudio-e2e-tests/redhat-appstudio-e2eCategory: Logs:
|
|
/retest |
098fb6e to
a198c5c
Compare
🤖 Pipeline Failure AnalysisCategory: Timeout Pipeline job failed due to the end-to-end tests exceeding the allocated timeout. 📋 Technical DetailsImmediate CauseThe Contributing FactorsWhile no specific test failures were reported, the ImpactThe timeout failure prevented the completion of the end-to-end test suite for this pull request, meaning the quality and correctness of the infrastructure changes could not be validated. This blocked the progression of the CI/CD pipeline for the affected changes. 🔍 Evidenceappstudio-e2e-tests/redhat-appstudio-e2eCategory: Logs:
|
|
@aThorp96: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
a198c5c to
9778afd
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aThorp96, flacatus, infernus01 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
9778afd to
4adb4b6
Compare
|
New changes are detected. LGTM label has been removed. |
🤖 Pipeline Failure AnalysisCategory: Infrastructure Pipeline failed due to persistent DNS resolution errors preventing the cluster from being reached by diagnostic and test execution steps. 📋 Technical DetailsImmediate CauseSeveral diagnostic and data collection steps, including Contributing FactorsThe primary test execution step, ImpactThe inability to resolve the Kubernetes API server's DNS name prevented the successful execution of critical data gathering steps, significantly hindering the ability to diagnose further issues. It also directly contributed to the termination of the main e2e test execution, causing the entire pipeline run to fail. 🔍 Evidenceappstudio-e2e-tests/gather-audit-logsCategory: Logs:
|
4adb4b6 to
b1c3276
Compare
🤖 Pipeline Failure AnalysisCategory: Infrastructure Pipeline failed due to intermittent DNS resolution errors preventing access to the Kubernetes API server, which impacted multiple diagnostic and deployment steps. 📋 Technical DetailsImmediate CauseMultiple steps, including Contributing FactorsThe ImpactThe inability to resolve the Kubernetes API server's hostname prevented these diagnostic steps from collecting essential cluster information and configurations. This lack of diagnostic data could hinder debugging efforts for any other potential issues. Furthermore, it highlights a critical infrastructure instability within the testing environment that could affect the reliability of all subsequent tests and deployments. 🔍 Evidenceappstudio-e2e-tests/gather-audit-logsCategory: Logs:
|
The previous image,
quay.io/openshift-pipeline/pipelines-serve-tkn-cli-rhel9@sha256:ac27f336d3e4e9e2538a867c1a956ca8328428948dd72d9ad6456c346ab48989seems to have disappeared from quay.io. While we investigate the issue and rollout the next release, this should get CI working again by overriding the image to a more recent version. Since tkn-cli-serve is unused by Konflux, this just needs to exist so the deployment can succeed